Avoid generating properties based on synthetic bridge methods #106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Java 5 supports covariant return types, which if overridden cause the compiler to generate "bridge" methods: https://stackoverflow.com/questions/14694852/can-overridden-methods-differ-in-return-type
These methods appear in
Class.getDeclaredMethods()
and if they happen to appear before the true non-bridge method, then they can causeBeanBuilder
either to:On my machine (Java 1.8.0_181-b13 on Mac), the failing test cases produce two distinct errors:
Solution
Skip over all synthetic and bridge methods as is done in databind's
AnnotatedMethodCollector
.